Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lower latenct-monitor-threashold in expire-cycle test case #1584

Open
wants to merge 2 commits into
base: unstable
Choose a base branch
from

Conversation

zuiderkwast
Copy link
Contributor

The test case checks for expire-cycle in LATENCY LATEST, but with the new hash table, the expiry-cycle is too fast to be logged by latency monitor. Lower the latency monitor threshold to make it more likely to be logged.

Fixes #1580

and fix merge conflict markers

Signed-off-by: Viktor Söderqvist <[email protected]>
Copy link

codecov bot commented Jan 19, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.96%. Comparing base (2d0b8e3) to head (b0a3f41).

Additional details and impacted files
@@             Coverage Diff              @@
##           unstable    #1584      +/-   ##
============================================
+ Coverage     70.94%   70.96%   +0.01%     
============================================
  Files           121      121              
  Lines         65132    65132              
============================================
+ Hits          46207    46218      +11     
+ Misses        18925    18914      -11     

see 11 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Test failure] LATENCY of expire events are correctly collected (unit/latency-monitor)
2 participants